Hello @Syed Chishty ,
Welcome to Microsoft Q&A, and thank you for describing the issue.
According to the Azure AI Content Understanding documentation for the GA 2025-11-01 API version, barcode extraction is supported for document-based analyzers.
I would recommend checking the following settings.
First, verify that your analyzer uses a document-compatible base analyzer, such as:
"baseAnalyzerId": "prebuilt-document"
You may also verify whether your analyzer is based on prebuilt-read or prebuilt-layout.
If the analyzer uses prebuilt-image, barcode extraction might not work in the same way because image analyzers are not intended for document content extraction.
Next, check the analyzer configuration and confirm that barcode extraction is enabled:
"config": {
"returnDetails": true,
"enableBarcode": true
}
The enableBarcode option detects and extracts barcodes and QR codes. It is enabled by default for document-based analyzers, but I would recommend confirming that it has not been explicitly set to false.
The figure-related settings are separate from barcode extraction. Options such as enableFigureDescription and enableFigureAnalysis are used for charts, diagrams, and figures. Barcode extraction is controlled by enableBarcode.
Please also check where you are looking for the barcode result. Barcodes are not returned as custom schema fields. They are returned in the barcode collection inside the document analysis response.
A detected barcode result can include:
Barcode type
Decoded value
Confidence score
If you recently moved from a preview API version to the GA 2025-11-01 version, I would also recommend reviewing and recreating the analyzer definition. The GA version requires an explicit models object in the analyzer configuration.
You should also confirm that the barcode format is supported. Supported formats include QR Code, PDF417, UPC-A, UPC-E, Code 39, Code 128, EAN-8, EAN-13, and other documented barcode types.
If you use Markdown output, the barcode can appear in the following format:

Finally, you can test the same document in Content Understanding Studio and verify whether the barcode is detected in the visual result before comparing it with the API response.
I hope these recommendations help.